Transfer of synchronization in a hybrid global navigation satellite packet network system

ABSTRACT

Networks, network devices and methods of synchronization using transfer of synchronization packets are provided. Some network devices are configured to use either a timing reference extracted based on GPS signals or an imported timing reference, as an operative time reference. A network device from which to import the time reference is selected and may be updated to meet a selection rule related to the quality of receiving the transfer of synchronization packets.

RELATED APPLICATIONS

This application is a continuation of, and claims priority from, U.S.patent application Ser. No. 14/035,248, filed on Sep. 24, 2013, which isa continuation of, and claims priority from, U.S. patent applicationSer. No. 13/015,077, filed on Jan. 27, 2011, entitled “Transfer ofSynchronization in a Hybrid Global Navigation Satellite Packet NetworkSystem”, the disclosure of which is incorporated here by reference.

TECHNICAL FIELD

The present invention generally relates to networks, network devices andmethods used for the distribution of synchronization derived from aglobal navigation satellite system (GNSS), and, in particular, to thetransfer of synchronization in a hybrid GNSS packet network system.

BACKGROUND

Deploying stand alone global positioning satellite (GPS) receivers ateach base transceiver station (BTS) cell-site is a technique that haslong been used to provide precision time synchronization having accuracybetter than 1 microsecond (ρs). For example, in the Code DivisionMultiple Access (CDMA) networks, the deploying of stand-alone GPSreceivers at each cell-site has been used for over 15 years.

The Global Positioning System is a space-based global navigationsatellite system (GNSS) that allows inferring reliable location and timeinformation in all weather at a GPS receiver on the surface of theEarth, if there is an unobstructed line of sight from the GPS receiverto plural satellite vehicles (SVs). A GPS signal includes a number ofparameters specific to the SV emitting the GPS signal, which parameterscan be used to compute the precise location of the GPS receiver and aprecise timing offset of the GPS receiver's clock to a time referencetraceable to a common timebase. Thus, the GPS receiver can synchronizeits timing with a network of GPS receivers, relative to a commontimebase. A GPS receiver that is demodulating GPS signals received fromplural SVs such that precise timing can be extracted is said to belocked.

In older systems, the antenna component of a GPS receiver had to have anunobstructed view of the SVs, for example, to be located on top of highbuildings. Traditionally, there were two performance figures of meritregarding link margin of a GPS receiver: the acquisition sensitivity andtracking sensitivity. The acquisition sensitivity is the minimum signalquality carrier to noise ratio (C/No) required to demodulate and lock toa GPS signal from power-on; the tracking sensitivity is the minimum C/Norequired to maintain lock after the GPS signal acquisition has beenachieved. The tracking sensitivity benefits from the availability of theSV parameters in the GPS signal demodulated by the GPS receiver. Anotherfigure of merit associated with acquisition is the time required by aGPS receiver to achieve lock, this time being often referred to as theTime-to-First-Fix (TTFF). An Aided-GPS (A-GPS) operation uses networkresources to send SV parameters to the GPS receiver in order to improvethe acquisition sensitivity and the TTFF. This is of a benefit in poorsignal conditions, for example in a city, where the GPS signals maysuffer multipath propagation due to bouncing off buildings, or may beweakened by passing through various materials. Additionally, the C/Nocan be easily degraded by the presence of interfering jamming signals(intentional or not) due to the extremely low power of the GPS signal.The A-GPS technology has yielded a substantial improvement in theacquisition sensitivity, allowing the use of GPS receivers in moreconvenient physical location, e.g., inside of buildings. In an A-GPSreceiver located in a degraded signal environment, an improvedacquisition link margin offsets penetration losses and other degradationimpairments of the GPS signals. However, since the penetration lossesimpairments are difficult to predict exactly, there is an increaseduncertainty as to whether the GPS link margin will be (and will remain)adequate for a given deployment. Thus, an adequate margin for aparticular deployment cannot be guaranteed. Additionally, the accuracyof the timing extracted from a degraded signal environment may also bedegraded.

To summarize, although the A-GPS technique improves the GPS signalacquisition link margin, capitalizing on the A-GPS performance andrelaxing the GPS antenna deployment provisioning rules, the A-GPStechnique introduces an unacceptable uncertainty in the resultant linkmargin that limits its applicability in telecom products.

Packet-based synchronization methods such as the ones set forth in theIEEE-1588 standard have recently promised to substantially reduce thecost and improve the reliability of precision time synchronization. Thepredominant architecture associated with packet-based synchronization isto deploy a few timing servers (masters) within a network, the timingservers distributing timing to hundreds of clients (slaves). The timingservers are usually network devices distinct from the base stations(BTSs).

FIG. 1 illustrates packets messages involved with the IEEE-1588 (theJanuary 2011 version of which is incorporated herewith by reference)method of transferring time synchronization between a master 10 and aslave 20, the sequence of operations being represented by via downwardstime lines. The master 10 sends a SYNC message and embeds a masteregress time (T1) according to the master clock in the SYNC packet'spayload. The slave 20 receives the SYNC packet and marks a slave ingresstime locally (T2) according to the slave clock. The slave 20 then sendsa DELAY_REQUEST message (marking a slave egress time as T3 according tothe slave clock). The master 10 marks a master ingress time (T4) of theDELAY_REQUEST message according to the master clock, and then sends amessage DELAY_RESPONSE embedding T4 in the DELAY_RESPONSE packet'spayload. The master egress time (i.e., the timestamp) T1 may be conveyedwith a message called a FOLLOW_UP, according to a method referred to asa two-step clock. The SYNC and DELAY_REQUEST messages are termed “Event”messages since their delivery is time-stamped at both egress andingress, whereas the FOLLOW_UP and DELAY_RESPONSE messages are referredto as “General” messages. Messages may be transported on a variety ofcommunication protocols, for example, as Ethernet packets. The intervalT4-T1-(T3-T2) represents the round trip propagation delay, which may beconsidered twice the single propagation delay (Tprop). Once thepropagation delay (Tprop) is known by the slave 20, Tprop can be removedfrom T1 to synchronize the slave clock with the master clock. The keyimpairment to accurate synchronization over Ethernet networks is packetdelay variation that may occur when a packet carrying an Event messageencounters queuing delay.

The transfer of synchronization packets may convey frequency informationand timing information. For the frequency information, only one-waycommunication is necessary, whereas for timing information two-waycommunication is required. Thus, in order to convey frequencyinformation, reception of SYNC packet would suffice.

Since timing servers are expensive, they are typically deployed to servea large number of clients. A fundamental problem with packet-basedmethods is that controlling the packet delay variation (PDV) over alarge number of hops (which large number is inherent in thisarchitectural model) is difficult without deploying specializedswitching nodes that account for the internal packet delay. The PDV is akey metric to the delivery of adequate time synchronization accuracy.

Accordingly, it would be desirable to provide devices, systems andmethods that avoid the afore-described problems and drawbacks.

SUMMARY

In some of the following embodiments, network devices may use either atime reference extracted based on GPS signals or an imported timereference, as an operative time reference. The improvement inavailability and reliability of time references renders less stringentand important the requirement to have an expensive high-qualityoscillator in order to holdover synchronization when lock of the GPSreceiver is lost. Additionally, network devices may dynamically selectanother network device from which to import the time reference, based ona quality of receiving the transfer of synchronization packets fromplural available network devices exporting their time reference.

According to one exemplary embodiment, a network device includes aglobal position signal (GPS) receiver, a switching part, an operativepart and a controller. The GPS receiver is configured to receive GPSsignals and to determine a time reference based on the received GPSsignals. The switching part is configured to communicate transfer ofsynchronization packets. The operative part is configured to manageradio communication using an operative time reference. The controller isconfigured to switch the operative part between at least (i) a firstmode, in which the operative part uses, as the operative time reference,the time reference determined by the GPS receiver and (ii) a secondmode, in which the operative part uses, the operative time referencedetermined using one or more imported time references, each of theimported time references being extracted from the transfer ofsynchronization packets communicated with a network device, thecontroller switching the operative part between the first mode and thesecond mode depending on a quality of the received GPS signals and aquality of communicating the transfer of synchronization packets by theswitching part from each of at least one other network device,respectively. The GPS receiver may be an A-GPS receiver. The controllermay be configured to compare the time reference determined by the A-GPSreceiver and the imported time reference thereby enabling qualifying theoperative time reference. The controller may be configured select one ofthe at least one other devices and to determine the operative timereference to be an imported time reference corresponding to the selectednetwork device. The controller may also be configured to calculate theoperative time reference as a weighted average of at least two of thetime reference determined by the GPS receiver and the imported timereferences, wherein weights used to calculate the weighted averagedepend on the quality of the received GPS signals and the quality ofreceiving transfer of synchronization packets.

According to one exemplary embodiment, a radio communication networkincludes base stations each having a switching part configured tocommunicate transfer of synchronization packets, the switching partbeing configured to process the communicated transfer of synchronizationpackets with highest priority, and an operative part configured tomanage radio communication using an operative time reference. At leastsome of the base stations have a global position signal (GPS) receiverconfigured to receive GPS signals and to determine a time referencebased on the received GPS signals, and a controller configured to switchthe operative part between at least (i) a first mode, in which theoperative part uses, as the operative time reference, the time referencedetermined by the GPS receiver and (ii) a second mode, in which theoperative part uses the operative time reference determined using one ormore imported time references, each imported time reference beingextracted from the transfer of synchronization packets communicated witha network device, the controller switching the operative part betweenthe first mode and the second mode depending on a quality of thereceived GPS signals and a quality of receiving the transfer ofsynchronization packets by the switching part from each of at least onenetwork device, respectively.

According to another exemplary embodiment a method of determining anoperative time reference in a GPS equipped radio communication device ofa network including at least two other GPS equipped radio communicationdevices is provided. The method includes receiving GPS signals,evaluating quality of the GPS signals, and determining a time referencebased on the received GPS signals, if the quality of the received GPSallows. The method further includes receiving transfer ofsynchronization packets from at least one GPS equipped network device,evaluating a quality of receiving the transfer of synchronizationpackets for each of the at least one GPS equipped network devices fromwhich transfer of synchronization packets have been received, selectingone network device among the at least one GPS equipped network devicesfrom which transfer of synchronization packets have been received basedon the evaluated quality, and determining an imported time referencefrom the transfer of synchronization packets received from the selectedone network device. The method also includes determining whether to usethe time reference or the imported time reference as the operative timereference, based on the evaluated quality of the received GPS signalsand the quality of receiving the transfer of synchronization packetsfrom the selected one network device.

According to another exemplary embodiment, a network device has aswitching part configured to communicate transfer of synchronizationpackets, an operative part and a controller. The operative part isconfigured to manage radio communication using an operative timereference, the operative time reference being based on informationextracted from the transfer of synchronization packets received from atleast two network device. The controller is configured (i) to monitor aquality of receiving the transfer of synchronization packets for each ofthe at least two network devices, and (ii) to determine the operativetime reference using one or more imported time references, each timereference being extracted from the transfer of synchronization packetsreceived from a network device among the at least two network devicesbased on the monitored quality of communicating.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the specification, illustrate one or more embodiments and,together with the description, explain these embodiments. In thedrawings:

FIG. 1 is an illustration of the IEEE-1588 method of transferring timesynchronization;

FIG. 2 is a schematic diagram of a network according to an exemplaryembodiment;

FIG. 3 is a schematic diagram of a network device according to anexemplary embodiment;

FIG. 4 is a graph illustrating a delay distribution for packetstransmitted between two network devices according to an exemplaryembodiment;

FIG. 5 is a schematic diagram of network devices in a network accordingto an exemplary embodiment;

FIG. 6 is a schematic diagram of network devices in a network accordingto another exemplary embodiment;

FIG. 7 is a schematic diagram of network device according to anexemplary embodiment; and

FIG. 8 is a flow diagram of a method according to an exemplaryembodiment.

DETAILED DESCRIPTION

The following description of the exemplary embodiments refers to theaccompanying drawings. The same reference numbers in different drawingsidentify the same or similar elements. The following detaileddescription does not limit the invention. Instead, the scope of theinvention is defined by the appended claims. The following embodimentsare discussed, for simplicity, with regard to the terminology andstructure of a communication network in which some network devicesimport timing synchronization from other network devices that exporttiming synchronization. The embodiments to be discussed next are notintended to be limiting, a flexible distributed timing synchronizationbeing applicable to other systems.

Reference throughout the specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with an embodiment is included inat least one embodiment of the present invention. Thus, the appearanceof the phrases “in one embodiment” or “in an embodiment” in variousplaces throughout the specification is not necessarily all referring tothe same embodiment. Further, the particular features, structures orcharacteristics may be combined in any suitable manner in one or moreembodiments.

According to an exemplary embodiment illustrated in FIG. 2, in a network100, timing synchronization is performed based on high priority transferof synchronization packets sent by network devices operating aspacket-based synchronization servers (PSSs) such as 110, 120 to networkdevices operating as packet-based synchronization clients (PSCs) such as112, 114, 116, 118, 122, 124, 126, 128, 130, and 132. The networkdevices operating as PSSs or as PSCs may be base stations (BTSs).However, the inventive concept is not limited by the functionality ofthe network devices. The transfer of synchronization packets may beperformed in a manner similar to the IEEE-1588 method of transferringtime synchronization illustrated in FIG. 1, but it is not limitedthereof.

All the network devices illustrated in FIG. 2 may have the structureillustrated in FIG. 3. A network device 150 includes a GPS receiver 160,a switching part 170, an operative part 180 and a controller 190. TheGPS receiver 160 is configured to receive GPS signals and to determine atime reference based on the received GPS signals. The GPS receiver 160may be an A-GPS receiver. The switching part 170 is configured toreceive and to send transfer of synchronization packets. The operativepart 180 is configured to manage radio communication using an operativetime reference. However, the embodiments are not limited by radio(wireless) communication, that is, some of the network devices may also(or exclusively) communicate via wire.

The controller 190 is configured to switch the operative part 180between at least (i) a first mode in which the operative part 180 uses,as the operative time reference, the time reference determined by theGPS receiver 160 and (ii) a second mode in which the operative part 180uses, as the operative time reference, an imported time referenceextracted from the transfer of synchronization packets received from aselected network device. The controller 190 switches the operative part180 between the first mode and the second mode depending on a quality ofthe received GPS signals and a quality of receiving transfer ofsynchronization packets by the switch 170 from other network devices,respectively. The controller 190 may be configured to switch off the GPSreceiver 160 when the operative part 180 does not operate in the firstmode. Also, the controller 190 may control the switching part 170 tosend transfer of synchronization packets based on the time referencedetermined by the GPS receiver 160 to other network devices (i.e., toexport its time reference).

In various embodiments, depending on the specific functionality of theoperative part 180, the extracting of the imported time reference mayrequire frequency information or timing information. If only frequencyinformation is required, then only one-way communication (e.g., Eventmessages and associated General messages sent from PSS to PSC) isnecessary. If timing information is required, then a two-waycommunication (e.g., Event messages and associated General messages fromPSS to PSC and from PSC to PSS) is necessary. The controller 190 may beconfigured to control the switching part 170 to communicate thenecessary messages in order to ensure gather the transfer ofsynchronization packets necessary to extract the frequency informationor the timing information. In order to maintain the synchronization, thetransfer of synchronization packets are sent by the PSS at regular timeintervals, which may be calibrated based on various factors such as thefraction of packets that do not experience queuing delays and the amountof time a clock of the network device operating as a PSC can run withoutdeviating (e.g., a local oscillator may drift due to noise ortemperature effects). On the one hand, the time intervals should not betoo small because this would result in more packets than necessary andwastefully congest the network. In the case of two-way communication, atime interval between related packets may be different from a timeinterval between un-related packets. The network device operating as aPSC may dynamically negotiate the time interval(s).

For the purpose of illustration, the network devices in FIG. 2 havetheir controller marked as PSS, when the controller switches theoperative part to operate in the first mode, and have their controllermarked as PSC, when the controller switches the operative part tooperate in the second mode. All the network devices in FIG. 2 areillustrated as having a GPS receiver. However, the network 200 mayinclude also the network devices not equipped with a GPS receiver.

The network 100 includes network devices equipped with GPS receiversthat may operate both in the first mode and, alternatively, in thesecond mode. The flexibility of timing synchronization occurs if thereare at least two network devices capable to operate as PSSs. In contrastwith the networks that use dedicated timing servers and where a timingserver exports its time reference to a large number of network devices,in the network 100, plural network devices are configured to serve asPSSs. In one embodiment, the GPS equipped network devices maypreferentially operate in the first mode, but if necessary (e.g., iftheir GPS receiver is unable to lock) may operate in the second mode,using time references from other network devices. Due to a large numberof available time references, the network 100 inherently andstatistically provides the basis for an enhanced synchronization for anynetwork device that is not equipped with a GPS receiver or is unable touse its own GPS based time reference.

In the network 100, the switching parts of the network devices areconfigured to process received packets based on a priority associated toeach packet, the transfer of synchronization packets having the highestpriority. The network devices 110, 112, 114, 116, 118, 120, 122, 124,126, 128, 130, and 132 may be base stations.

The network devices that operate as PSSs have each an active GPS sectionconfigured to receive GPS signals from plural satellite vehicles (SVs)110 a, 110 b, 110 c, 120 a, 120 b, 120 c, and to extract theirrespective time reference based on the GPS signals. The network devicesthat operate as PSCs may also have each a GPS receiver, but their GPSreceivers may not be actively used. However, at least some of thenetwork devices in the network 100 are capable (i) to perform intrinsicGPS timing synchronization (i.e., first mode), (ii) to import timingsynchronization as a packet-based client (PSC) (i.e., second mode), and(iii) to export packet-based timing synchronization as a packet-basedserver (PSS). Therefore, the network 100 as a whole provides enhancedcapabilities and dynamic adaptability to traffic conditions due to theflexibility resulting from multi-timing server and dual possibleoperation of at least some of the network devices.

Each network device in FIG. 2 has a switching part (SW) configured toreceive packets from other network devices. The transfer ofsynchronization packets has the highest priority, the synchronizationpackets being processed as soon as possible. The lines between thenetwork devices in FIG. 2 show transfer paths of the transfer ofsynchronization packets. A network device operating as a PSC may receivetransfer of synchronization packets from more than one network deviceoperating as a PSS (see, e.g., the network device 132 in FIG. 2,receiving transfer of synchronization packets from both the networkdevice 110 and the network device 120).

Thus, in the network 100, the timing synchronization function isdecentralized being performed by more than one network device operatingas timing servers (PSSs). A network device operating as a PSC (or morespecifically the controller of this network device) may select a timingserver (PSS) among the network devices whose transfer of synchronizationpackets are received at the network device operating as a PSC, based ona minimum packet delay variation (PDV). The PDV is a variation of thepacket propagation delay between a PSS and a PSC that may import thetime reference from the PSS. FIG. 4 is a graph illustrating a delaydistribution for packets transmitted between two network devices (one ofwhich may be PSS and the other may be PSC). In this graph, a peak 200corresponds to packets experiencing no spurious delays, while the bellshaped part 205 of the distribution corresponds to delayed packets.

In selecting the PSS, the PSC may consider only a “golden” group ofpackets that have a high PDV quality (e.g., in the peak 200) as thesepackets experience no queuing delays between source (e.g., a PSS) anddestination (e.g., a PSC). Achieving a good performance based on thiscondition means not only to have a small number of hops (e.g.,intermediate network devices) between the PSS and the PSC, but also thatno unpredictable delays due to disturbing traffic are expected toappear. Disturbing traffic are packets unrelated to the synchronizationlink. Some of these packets may require a long time for processing.Although the timing packet has a higher priority than such a packet ofthe disturbing traffic, the switch of an intermediate network device maynot be able to process the timing packet before finishing processing thepacket of the disturbing traffic. This results in a non-deterministicqueuing delay yielding an increased PDV for the transfer ofsynchronization packets.

In one embodiment, a network device performing as PSS may have atraditional GPS receiver antenna deployed to have a clear-sky view. Thenetwork devices operating as a PSC selects one of the PSSs in thenetwork relative to which to perform timing synchronization, theselected PSS being within a limited number of hops and subject to aminimum PDV criterion.

Most of the network devices that have a GPS receiver frequently alsohave an internal high-stability oscillator that allows the networkdevice to holdover the timing synchronization when the lock of the GPSreceiver is lost, for example, due to an obstruction interposing in theGPS signal paths. According to an embodiment, whose operation isillustrated in FIG. 5, an impaired network device 210, whose GPSreceiver has lost lock, e.g., due to a blockage illustrated as solidline 230, imports a time reference from a network device 220 operatingas a PSS, whose GPS receiver is unobstructed and locked. For example,the network device 220 has a clear-sky view to SVs 220 a, 220 b and 220c, while the network device 210's view of SVs 220 a, 220 b, and 220 c isobstructed. The improvement in availability and reliability of timereferences renders less stringent and important the requirement to havean expensive high-quality oscillator in order to holdoversynchronization when lock of the GPS receiver is lost.

According to another embodiment, in a network, most of the networkdevices have either a degraded view or an obstructed view, and eachnetwork device has an A-GPS receiver section. In FIG. 6, a networkdevice 310 has a degraded view to SVs 310 a, 310 b, 310 c, for example,due to multiple path reflections and penetration loss. This degradationis symbolically illustrated by a dashed line 312. Another network device320 has its view to SVs 320 a, 320 b, 320 c obstructed. This obstructionis symbolically illustrated by a solid line 322. The network device 310may receive transfer of synchronization packets from other networkdevices that have degraded views, but that are able to compile a validtime reference due to the A-GPS receiver sections. A controller of thenetwork device 310 may compare the accuracy of a time referenceextracted based on the received GPS signals using A-GPS technology, withimported time references from one or more other network devices in orderto qualify and, thereby, improve the reliability of the extracted timereference. The controller of the network device 310 may also beconfigured to trigger an alarm when the comparing indicates that adifference between the time reference determined based on the receivedGPS signals and an imported time reference exceeds a predeterminedvalue. The controller may then employ additional methods to quantify thedifference and to correct the time reference determined based on thereceived GPS signals, if possible. The network device 310 may meanwhilealso export its GPS time reference to other network devices, thusoperating both as a PSS and as a PSC.

The controller of the network device 310 may switch the operative partto operate in a third mode in which the operative part uses, as theoperative time reference, an weighted average of at least two of thetime reference determined based on the receiver GPS signals and importedtime references, each imported time reference being extracted from thetransfer of synchronization packets received from a network device. Theweights may depend on a quality of the received GPS signals and aquality of receiving transfer of synchronization packets by the switchfrom other network devices, respectively.

A controller of a network device that can operate both as a PSS and as aPSC may also be configured select a new PSS among the network devicesfrom which a switching part of the network device receives transfer ofsynchronization packets, based on the same selection rule, when aselected PSS no longer meets the selection rule or is no longeravailable.

As mentioned above, a network device 350 without a GPS receiver may be apart of the network 100 and benefit from availability of plural PSSs.The structure of the network device 350 is illustrated in FIG. 7. Thenetwork device 350 includes a switching part 370, an operative part 380and a controller 390. These components may be hardware, firmware,software or a combination thereof. The switching part 370 is configuredto receive transfer of synchronization packets from plural networkdevices operating as PSSs. The operative part (380) is configured tomanage radio communication using an operative time reference. Theoperative time reference is an imported time reference extracted fromthe transfer of synchronization packets received from a selected PSS.The controller (390) is configured (i) to monitor a quality of receivingtransfer of synchronization packets from each of at least two networkdevices operating as PSSs and (ii) to select a PSS from the at least twonetwork devices based on a selection rule linked to the quality ofreceiving the transfer of synchronization packets.

The selection rule used by the controller 390 to select a PSS may bethat the transfer of synchronization packets received from the selectedPSS to have a smallest packet delay variation (PDV) among packet delayvariations corresponding to the at least two network devices operatingas PSSs. The controller 390 may select network device from which theswitching part receives transfer of synchronization packets, based onthe selection rule, when the selected PSS no longer meets the selectionrule or is no longer available.

A flow chart of a method (400) of determining an operative timereference in a GPS equipped radio communication device of a networkincluding at least two GPS equipped radio communication devices isillustrated in FIG. 8. The method 400 may be performed by any networkdevice in FIG. 2. The method 400 includes receiving GPS signals, atS410, and evaluating a quality of the received GPS signals, at S420.Further the method 400 includes determining a time reference based onthe received GPS signals if the quality of the received GPS allows, atS430.

The method 400 also includes receiving transfer of synchronizationpackets from at least one GPS equipped network device at S440, andevaluating a quality of receiving the transfer of synchronizationpackets for each of the at least one GPS equipped network devices fromwhich transfer of synchronization packets have been received, at S450.The method 400 further includes selecting one network device among theat least one GPS equipped network devices from which transfer ofsynchronization packets have been received based on the evaluatedquality, at S460) and determining an imported time reference from thetransfer of synchronization packets received from the selected onenetwork device, at S470. Note that the operations at S410, S420 and S430may be executed in parallel with the operations at S440, S450, S460 andS470.

The method 400 finally includes determining whether to use the timereference or the imported time reference as the operative timereference, based on the evaluated quality of the received GPS signalsand the quality of receiving the transfer of synchronization packetsfrom the selected one network device at S480.

The method 400 may be stored as executable codes on a computer readablemedium. The computer readable medium may be hard and floppy disk drives,CD-ROM drives, and other hardware capable of storing information.

An advantage of some embodiments is the flexibility of using self-GPSbased time references or imported time references. Also, someembodiments may both take advantage of the time references exported byGPS equipped network devices that have a clear-sky view when these areavailable, and compensate for the absence of a reliable time referenceusing A-GPS technology. In addition, some embodiments select the networkdevice from which the time reference is imported based on the PDV and onan expected absence of disturbing traffic, thus, taking advantage ofcurrent traffic information. Embodiments may update the selection of anetwork device from which to import the time reference, thereby havingthe advantage of adaptability. Sometimes, it may be necessary to modifythe path through which transfer of synchronization packets are receivedin order to satisfy the required PDV performance.

When a GPS receiver loses its lock to the GPS signals, an alternative tothe use of a high quality expensive oscillator (that can sustainopen-loop time synchronization typically for a period of 8-24 hours) isprovided by importing the time reference from another network device.Since higher synchronization reliability and availability is achieved,the provisions for holdover, in particular the quality of theoscillator, can be relaxed substantially, allowing the use of cheaperoscillators.

The redundant packet-based synchronization methods according to variousembodiments used in conjunction with A-GPS provides: 1) redundancy toguarantee synchronization availability suitable with telecom standards;2) improve/audit the accuracy of the A-GPS derived time synchronizationattached to the local BTS against an ensemble of neighbor A-GPS or GPSBTS references imported via the packet network.

The disclosed exemplary embodiments provide networks, network devicesand methods of synchronization using transfer of synchronizationpackets, in which some network devices may use either a time referenceextracted based on GPS signals or an imported time reference as anoperative time reference or both. It should be understood that thisdescription is not intended to limit the invention. On the contrary, theexemplary embodiments are intended to cover alternatives, modificationsand equivalents, which are included in the spirit and scope of theinvention as defined by the appended claims. Further, in the detaileddescription of the exemplary embodiments, numerous specific details areset forth in order to provide a comprehensive understanding of theclaimed invention. However, one skilled in the art would understand thatvarious embodiments may be practiced without such specific details.

1-36. (canceled)
 37. A network device comprising: a switching partconfigured to communicate transfer of synchronization packets; anoperative part configured to manage radio communication using anoperative time reference, the operative time reference being based oninformation extracted from the transfer of synchronization packetsreceived from at least two network devices; and a controller configuredto monitor a quality of communicating transfer of synchronizationpackets for each of the at least two network devices; and to determinethe operative time reference using one or more imported time references,each time reference being extracted from the transfer of synchronizationpackets received from a network device among the at least two networkdevices based on the monitored quality of communicating.
 38. The networkdevice of claim 37, wherein the controller is configured to determinethe operative time reference to be an imported time referencecorresponding to a selected network device among the at least twonetwork devices, and is further configured to determine the selectednetwork device based on a selection rule linked to the monitored qualityof communicating the transfer of synchronization packets from each ofthe at least two network devices.
 39. The network device of claim 38,wherein the selection rule is the transfer of synchronization packetsreceived from the selected network device to have a smallest packetdelay variation among packet delay variations corresponding to the atleast two network devices.
 40. The network device of claim 38, whereinthe controller is further configured to select a new network deviceamong the at least two network devices with which the switching partcommunicates the transfer of synchronization packets, based on theselection rule, when the selected network device no longer meets theselection rule or is no longer available.
 41. The network device ofclaim 38, wherein the transfer of synchronization packets includepackets used to extract frequency information.
 42. The network device ofclaim 38, wherein the transfer of synchronization packets includepackets used to extract frequency information and packets used toextract timing information.
 43. The network device of claim 38, whereinthe controller is configured to determine the operative time to be aweighted average of a plurality of time references, weights used tocalculate the weighted average being based on the monitored quality. 44.The network device of claim 37, wherein the switching part is configuredto process packets based on a priority associated to each packet, thetransfer of synchronization packets having the highest priority.
 45. Thenetwork device of claim 37, wherein the network device and the at leasttwo network devices are base stations.
 46. The network device of claim45, wherein the at least two network devices both include GPS receivers,which are used to generate the synchronization packets.
 47. A method fora network device comprising: communicating transfer of synchronizationpackets, including receiving the transfer of synchronization packetsfrom at least two network devices; monitoring a quality of thecommunicating transfer of synchronization packets for each of the atleast two network devices extracting one or more imported timereferences from the transfer of synchronization packets received from anetwork device among the at least two network devices based on themonitored quality of communicating; determining an operative timereference using the one or more imported time references; and managingradio communication using the determined operative time reference. 48.The method of claim 37, further comprising: determining the operativetime reference to be an imported time reference corresponding to aselected network device among the at least two network devices; anddetermining the selected network device based on a selection rule linkedto the monitored quality of communicating the transfer ofsynchronization packets from each of the at least two network devices.49. The method of claim 48, wherein the selection rule is the transferof synchronization packets received from the selected network device tohave a smallest packet delay variation among packet delay variationscorresponding to the at least two network devices.
 50. The method ofclaim 48, further comprising: selecting a new network device among theat least two network devices with which the network device communicatesthe transfer of synchronization packets, based on the selection rule,when the selected network device no longer meets the selection rule oris no longer available.
 51. The method of claim 48, wherein the transferof synchronization packets include packets used to extract frequencyinformation.
 52. The method of claim 48, wherein the transfer ofsynchronization packets include packets used to extract frequencyinformation and packets used to extract timing information.
 53. Themethod of claim 48, further comprising: determining the operative timeto be a weighted average of a plurality of time references, weights usedto calculate the weighted average being based on the monitored quality.54. The method of claim 47, further comprising: processing packets basedon a priority associated to each packet, the transfer of synchronizationpackets having the highest priority.
 55. The method of claim 47, whereinthe network device and the at least two network devices are basestations.
 56. The method of claim 55, wherein the at least two networkdevices both include GPS receivers, which are used to generate thesynchronization packets.